Link by Attribute

Why is it dangerous to link by other ways than by setting up a link attribute, and performing a "link by Attribute"?
I was warned at the Users Conference about using any other method, and most especially not to use "Drag and Drop". In fact, some of the more experienced DOORS administrators in large shops tell me that they delete all links nightly, and rebuild the next morning due to so many changes made daily.

So, when it says, "Delete all links", does it mean just "Delete all links between this module and the one I've linked to, or does it mean 'Delete all links in the database"? I don't think it does, but I'm afraid to try.

Also, how do I rejuvenate all the links the next day. Just do another "Link by Attribute"?
Thanks
Alice Brown
Sr. SQE
Right now, the administrator wants to know the nature of the 'corruption' that we would be protecting ourselves from by using the 'Link by Attribute' approach.
SystemAdmin - Wed Apr 01 17:06:28 EDT 2009

Re: Link by Attribute
Tony_Goodman - Thu Apr 02 02:56:54 EDT 2009

I have heard of admins rebuilding links overnight using link by attribute, but I thought that they did this because users entered ratget IDs rather than actualy creating the links themselves. Some one who does this might be able to explain the reasoning behind this approach.

I have never heard of drag and drop linking being dangerous. OK it is easy to make a mistake, but these can be easily rectified surely?

The most important safeguard you need is to ensure that your linkset pairings are set up as mandatory and that all folders in your project contain a soft-deleted DOORS Links module, then at least user can only create links to the wrong object, not the wrong module (or the wrong direction.

Also, ban users from wearing woolly gloves at work :-)

Re: Link by Attribute
SystemAdmin - Thu Apr 02 09:15:55 EDT 2009

The reason I remember this so well is because the response to the 'Drag n Drop' was so negative, with the safest method being that of 'Link by Attribute'. This from the Raytheon crowd and others who are longtime veterans of DOORS use. I agree with your point about the Link module being set up for exclusive use by the modules involved.
However, I still need to know: Does 'Delete All' only delete the links between the modules you've linked from THIS module? It doesn't make sense that it would delete all links in the database, but ALL is a very poor word for DOORS to use......The context could be This module or THIS project or THIS database.

Re: Link by Attribute
llandale - Thu Apr 02 13:19:38 EDT 2009

Our Raytheon partners have the philosophy that engineers specify their desired links in some attribute, and Raytheon runs a custom script nightly that creates links based on those attributes, deleting links that don't match. This custom script is a glorified link-by-attribute.

Solid practical reasons to do this involve the need to archive and restore modules; links are lost when doing so. If you have attributes representing the links the info is not lost. Also, module corruption or accidentally purging an link module are no longer disasters to the program.

There are some practical engineering reasons to do this.

The problem is the need for a solid philosophy on what sorts of objects can link to other sorts of objects, and the need for a massive custom link-by-attribute script to implement it. For example, a text attribute 'Links_TechSpecs' means the ObjIDs therein are to link to any valid requirement in any valid Tech Spec. Well, 'valid requirement' and 'valid tech spec' are both highly program specific concepts, that may change from program to program, requireing a big script that can handle those difference.

I wish I had the time to write such a script, and implement the philosophy here.

>Louie

Re: Link by Attribute
dpechacek - Thu Apr 02 15:52:55 EDT 2009

SystemAdmin - Thu Apr 02 09:15:55 EDT 2009
The reason I remember this so well is because the response to the 'Drag n Drop' was so negative, with the safest method being that of 'Link by Attribute'. This from the Raytheon crowd and others who are longtime veterans of DOORS use. I agree with your point about the Link module being set up for exclusive use by the modules involved.
However, I still need to know: Does 'Delete All' only delete the links between the modules you've linked from THIS module? It doesn't make sense that it would delete all links in the database, but ALL is a very poor word for DOORS to use......The context could be This module or THIS project or THIS database.

Running "Delete All Links" from the module "Link" menu will delete all inlink and outlinks coming into/going out of the module. It does not delete all links in the entire database (i cannot fathom who would ever want to do that).

Here we recreate some links nightly with a few scripts for active projects.

AAI Services, Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com

Re: Link by Attribute
SystemAdmin - Fri Apr 03 11:57:59 EDT 2009

Unfortunately, the message that pops up in DOORS 8.1 states: "This will delete all links to which you have access." I have access to many modules in many projects. So either the warning message is inaccurate, or I would indeed delete all links to which I have access. I assume they are referring to 'write access". In doesn't say, "Delete all links, only in these modules." And I don't have a test database separate from this one to chance that unhappy occurrence.

So , for DOORS 8.1, does that message refer to JUST the two modules I'm linking here, ALL the modules I'm linking from this module or "all the modules you have access to", as the message states?
Cheers,
Alice

Re: Link by Attribute
dpechacek - Mon Apr 06 08:24:35 EDT 2009

SystemAdmin - Fri Apr 03 11:57:59 EDT 2009
Unfortunately, the message that pops up in DOORS 8.1 states: "This will delete all links to which you have access." I have access to many modules in many projects. So either the warning message is inaccurate, or I would indeed delete all links to which I have access. I assume they are referring to 'write access". In doesn't say, "Delete all links, only in these modules." And I don't have a test database separate from this one to chance that unhappy occurrence.

So , for DOORS 8.1, does that message refer to JUST the two modules I'm linking here, ALL the modules I'm linking from this module or "all the modules you have access to", as the message states?
Cheers,
Alice

It deletes all links going into or going out of the module you run it from. It does not delete all links in the database. Or all links in the modules that the current module is linked to.

AAI Services, Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com

Re: Link by Attribute
kbmurphy - Mon Apr 06 11:54:38 EDT 2009

dpechacek - Mon Apr 06 08:24:35 EDT 2009
It deletes all links going into or going out of the module you run it from. It does not delete all links in the database. Or all links in the modules that the current module is linked to.

AAI Services, Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com

Alice--submit a bug report to IBM, because you're right, that message is confusing.

In their defense, though, you run it from the current module, and not from the DOORS Explorer. Still, that doesn't mean that the message is clear.

Re: Link by Attribute
dpechacek - Mon Apr 06 13:16:32 EDT 2009

kbmurphy - Mon Apr 06 11:54:38 EDT 2009
Alice--submit a bug report to IBM, because you're right, that message is confusing.

In their defense, though, you run it from the current module, and not from the DOORS Explorer. Still, that doesn't mean that the message is clear.

That would be an enhancement request Kevin. Not a bug report.

AAI Services, Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com

Re: Link by Attribute
SystemAdmin - Thu Apr 30 10:38:52 EDT 2009

llandale - Thu Apr 02 13:19:38 EDT 2009
Our Raytheon partners have the philosophy that engineers specify their desired links in some attribute, and Raytheon runs a custom script nightly that creates links based on those attributes, deleting links that don't match. This custom script is a glorified link-by-attribute.

Solid practical reasons to do this involve the need to archive and restore modules; links are lost when doing so. If you have attributes representing the links the info is not lost. Also, module corruption or accidentally purging an link module are no longer disasters to the program.

There are some practical engineering reasons to do this.

The problem is the need for a solid philosophy on what sorts of objects can link to other sorts of objects, and the need for a massive custom link-by-attribute script to implement it. For example, a text attribute 'Links_TechSpecs' means the ObjIDs therein are to link to any valid requirement in any valid Tech Spec. Well, 'valid requirement' and 'valid tech spec' are both highly program specific concepts, that may change from program to program, requireing a big script that can handle those difference.

I wish I had the time to write such a script, and implement the philosophy here.

>Louie

Having been a graduate of Raytheon Polytechnic Institute (Bedford, Sudbury, Waltham, Marlborough, Tewkesbury sites), I remember with fondness the excellent SD process we had there.
So, here's my question for you DOORS gurus: How do I get IBM/Telelogic/DOORS to make their 'Help' message clearer when they warn: "Delete all links will delete all links to which you have access." They don't really mean that, because I have access to links all over the database in many projects and folders. It means ONLY links from this module to any other module, as I have tested and found to be true in my test database.

Are there any gotchas toward this approach as we now only 'Link by Attribute'? The reason I ask this is because I discovered some old links showing up in our PRIME project because we were using one link module for several formal modules (a mistake). I have deleted those links from those test modules that showed up in our PRIME project, AND deleted the Link Attribute as well, trying to rid myself of the LINKS still showing up under Links. I cannot delete them, can't get rid of them, even thought the original links are gone. What do do?

Re: Link by Attribute
Ron_Lewis - Mon May 04 12:13:20 EDT 2009

SystemAdmin - Thu Apr 30 10:38:52 EDT 2009
Having been a graduate of Raytheon Polytechnic Institute (Bedford, Sudbury, Waltham, Marlborough, Tewkesbury sites), I remember with fondness the excellent SD process we had there.
So, here's my question for you DOORS gurus: How do I get IBM/Telelogic/DOORS to make their 'Help' message clearer when they warn: "Delete all links will delete all links to which you have access." They don't really mean that, because I have access to links all over the database in many projects and folders. It means ONLY links from this module to any other module, as I have tested and found to be true in my test database.

Are there any gotchas toward this approach as we now only 'Link by Attribute'? The reason I ask this is because I discovered some old links showing up in our PRIME project because we were using one link module for several formal modules (a mistake). I have deleted those links from those test modules that showed up in our PRIME project, AND deleted the Link Attribute as well, trying to rid myself of the LINKS still showing up under Links. I cannot delete them, can't get rid of them, even thought the original links are gone. What do do?

I am not sure what you said in this post but I am guessing that what you are saying is that you have links from objects that have be softdeleted.

If this is the case you will need to undelete the source object then delete the links before deleting the source object. Or you can purge the source objects.